SPEC-PWF-CON · v0.1 13 June 2026 Owner: Platform team
Drill-down of the master workflow map (SPEC-PWF). This process is a view over the spec — its requirements live in the PRD set, its events & services in the domain set, its entities in the ERD. Lanes, steps and events render from workflow/workflow-catalog.js — nothing is defined twice. The partner front door is its own drill-down (SPEC-PWF-PON); gaining a second capability later is capability & enrollment (SPEC-PWF-ENR).
1Trigger, outcome & lanes
What starts this process, where it ends, who acts and on which surfaces. A customer organization can be born two ways — owner self-sign-up at account.riversync.com, or Admin-provisioned off a won deal — and both converge on the same live, verified org.
RiverSync Co., Ltd. · BangkokSPEC-PWF-CON · 1 of 4
2The flow
Top to bottom in sequence; lanes are the actors. The first decision forks the two entry paths — self-serve sign-up versus an Admin-provisioned invite — which rejoin at email verification. Node shape follows the master conventions — pills start and end the process, grey nodes are backbone events, diamonds are decisions.
Customer onboarding — swimlane. Each step traces to a requirement in the table overleaf.SPEC-PWF-CON · flow
RiverSync Co., Ltd. · BangkokSPEC-PWF-CON · 2 of 4
3Steps
Each row is one node on the swimlane: who acts, what happens, the domain event it emits, and the requirement or rule it traces to.
RiverSync Co., Ltd. · BangkokSPEC-PWF-CON · 3 of 4
4Related documentation
Every id, event, service and entity this process touches — each linked to the document that owns it. This is how you hop from a step back to the requirement, the service or the data model behind it.
5Rules in play
The WF-rules that bind this workflow — the master holds the full set; the DM-rules (ERD) and SVC-rules (Domain) they extend stay with those documents.
6Open questions & ⚠ gaps
Surfaced by this process; not yet resolved in the model. To be reconciled into the PRD/ERD cascade.
Ref
Gap
TEN-4 ⚠
Self-registration & light RiverSync check. Owner-led self-sign-up and the post-verification legitimacy check are new — proposed requirement TEN-4 (self-registration) does not yet exist in the master PRD. Add it plus an ApplicationGating/limited-state model in the ERD.
ACC-5 ⚠
Email-verification gate spans all apps. The read-lock until EmailConfirmed is asserted here for every org surface, not just Account — confirm scope in ACC-5 and the claims layer (SVC-12).
ACC-6 ⚠
Invite & verification delivery. Owner invite and verification emails ride the unbuilt notifications capability (ACC-6).
7Revision history
Version
Date
Changes
0.1
13 Jun 2026
First draft — split from the former combined onboarding workflow (SPEC-PWF-ONB). Adds owner-led self-registration as a second entry path alongside Admin provisioning, plus the light RiverSync legitimacy check.
RiverSync Co., Ltd. · BangkokSPEC-PWF-CON · 4 of 4
